EDI Load form

Operations Vessel EDI Load EDI Load form

Administration EDI EDI Load EDI Load form

Prerequisites

The EDI Load form enables you to manually load an EDI message file. For example, if you receive a BAPLIE on a disk or as an email, you can use the EDI Load form to manually load that file.

Navis supports custom delimiters in EDI messages.

When you post a EDI COPRAR Load list file, N4 sets the flag ufvVerifiedForLoad to True for all containers included in the message and automatically selects the Is Verified For Load check box in the Sparcs Details form. If there is any load list discrepancy record, N4 sets the flag ufvVerifiedForLoad to False.

To see how manually loading an EDI message file fits into the rail process flow, see the Full Rail Operations and Lite Rail Operations process flows.

Prerequisites

To load an EDI message file:

  1. From the EDI Session drop-down list, select an inbound EDI session.

The EDI Session drop-down list contains only the EDI sessions defined under the EDI Configuration. Each entry in the drop-down list displays the EDI Session name followed by the EDI message type ID in parentheses.

  1. Click Browse, to locate the file on your computer or network.

  2. In the EDI Load dialog box, select the EDI message file. The complete path and the name of the selected file is displayed in the EDI File field.

  3. Optionally, select the Post Immediate check box, to post the EDI file immediately.

  4. If you do not select the check box, the file is posted when the selected EDI session is posted. If the Auto Post option is selected for the EDI session, the file is posted automatically. For more information, see EDI Session form (on page 1).

  5. Optionally, select the Additions Only check box and post a STOWPLAN message so that N4 checks for the new containers and adds only the new containers, if any, and ignores the other containers. The Additions Only option works only when you post a STOWPLAN message manually and does not work for EDI Jobs. Also, this option is not applicable when setting ARGOEDI012 (EDI_STOWPLAN_REPLACE_CONTAINERS) (on page 1) is set to true.

For example, if you select the option Additions Only and post a stowplan manually for the containers C1, C2, C3, and C4, in which C3 and C4 are already available, then N4 adds the new containers C1 and C2 and ignores containers C3 and C4, which are already available. 

  1. Optionally, select the check box Positions Only and post a STOWPLAN message so that N4 creates and updates the positions only for the new containers in the message. For already existing containers, N4 checks if there are any changes in the positions, and updates only the change in position for the existing containers. N4 records the event UNIT_POSITION_CORRECTION when the position update occurs. The Positions Only option works only when you post a STOWPLAN message manually and does not work for EDI Jobs. Also, this option is not applicable when setting ARGOEDI012 (on page 1) is set to true.

For example, if you select the Positions Only option and post a stowplan message manually for the containers C1, C2, C3, and C4, in which C3 and C4 are already available, then N4 executes the following:

  1. Optionally, select the Discharge Only check box and post the STOWPLAN message, so that N4 posts only the import and transshipment containers that must be discharged at the current port. The Discharge Only option works only for manual stowplan and does not work for EDI Jobs.

How this works: If you select Discharge Only check box and post a stowplan message, with category 'THRGH' for import containers, N4 completes the batch with a warning message stating that the batch is skipped. However, if the Discharge only check box is not selected, then N4 completes the batch by creating new units for the 'THRGH' import containers.

  1. Click Load.

Notes